home *** CD-ROM | disk | FTP | other *** search
- .po 0
- note: This is a transcript of the summary of RBBS bugs downloaded
- from Thomas Mack's "2nd Ring" BBS on 01/13/86
-
-
- ============= Reported Bugs/Problems ==============
-
- N O T E : These fixes are not part of the downloadable
- files on this or any other system. These fixes
- are supplied so that you may apply them to the
- copies of the .BAS programs you have.
- They will be included in the next offical release
- of RBBS-PC.
-
- PROGRAM EXT DATE DESCRIPTION/SOLUTION
- -------- --- -------- --------------------------------------------
- VERSION CPC13-1A
-
- RBBS-PC BAS 12/01/85 7:00PM First release of CPC13-1A
-
- RBBS-PC BAS 12/01/85 MNP protocol not available.
- EXE STATUS: Working on it. See 13-1A's
- documentation -- page 19, item 27.
-
- RBBS-PC BAS 12/01/85 Carrier drops on returning from "doors"
- EXE or DOS (SYSOP remote option 7).
- STATUS: Problem is with initialization done
- BASIC when RBBS-PC is loaded into memory but
- before RBBS-PC gets control. Working with
- Microsoft on this one.
-
- RBBS-PC BAS 12/10/85 RBBS-PC gives error 62 in line 5151. This is
- EXE caused by a PASSWRDS file that is not formatted
- correctly. The file must be in increments of
- three parameters each followed by either a ","
- or CR/LF. See 13-1A's documentation -- page
- 63, section 12.3.
- STATUS: There are three solutions.
-
- 1) Don't use the PASSWRDS file
- 2) Correct the passwrds file so that is format is
- correct.
- 3) Change line 13047 of RBBS-PC.BAS and recompile
- RBBS-PC.BAS.
- 13047 IF ERL = 5151 AND ERR = 62 THEN _
-
- RBBS-PC BAS 12/26/85 The sub-directory feature in CPC13.1A does not work
- EXE with the FILESEC file correctly. If you select
- the use of sub-directories then files will not
- match in the FILESEC file. This will be corrected
- in CPC13.1B.
- STATUS: As a temporary solution, add the
- additional sub-directory info to the filenames
- in the FILESEC file so that the routine will work.
-
- RBBS-PC BAS 12/27/85 SYSOP's can get the following following messages
- DOC when they try to drop to DOS remotely (SYSOP
- option 7) or exit to "doors":
- è
- Option 7 - "Remote exit to DOS not available."
- Option D - "All doors are locked!"
-
- This occurs because the SYSOP has set up his
- RBBS-PC to have the modem answer the phone
- (i.e. autoanswer) rather than RBBS-PC. This
- creates a security exposure for both of the
- above options.
-
- RBBS-PC CPC13-1A made available 4 ways for the
- program to answer modems.
-
- 1) Carrier detect (autoanswer/wait for carrier)
- 2) Ring Detect
- 3) Ringback (autoanswer/counts rings)
- 4) Dumb modem support (autoanswer/wait for carrier)
-
- CPC12-5B used only the Carrier detect (1) and
- ringback technique (3) to answer the phone. The
- use of any "autoanswer" method with either doors
- or option 7 created a secuirty exposure. Should
- the carrier drop when a SYSOP was in a door or
- option 7, the next caller (whoever it is) would
- have access to the system exactly where the SYSOP
- lost carrier because the modem (not RBBS-PC) was
- answering the phone.
-
- This is the reason ring detect answering (2) was
- put back into RBBS-PC CPC13-1A. If the modem is
- initialized to count rings instead of autoanswering
- then no security breach is possible for doors or
- the SYSOP opton 7. To help the SYSOP know which
- kind of system he has selected RBBS-PC CPC13-1A
- provides the following description on the initial
- screen:
-
- "WAITING FOR CARRIER" (modem set for auto answer)
- "WAITING FOR RING 1" (RBBS-PC counts and answers)
- "WAITING FOR RING X" (Ringback number of rings)
-
- To insure that SYSOPS do not accidently open their
- systems to destruction RBBS-PC will not allow the
- use of Option - 7 or Doors if the SYSOP has selected
- WAITING FOR CARRIER to answer the phone.
-
-
- STATUS: The solution is to use Ring detect. Run
- Config (1.9) and go to screen #1, parameter 9.
- Specify 1 ring and no for do you want ringback.
-
- Section 7.1.6 of the documentation will be re-
- written to incorporate the above information.
-
- RBBS-PC BAS 12/28/85 In SNOOP mode some SYSOPS using CPC13-1A report
- EXE that they cannot see what they type in and only
- some of what RBBS-PC is displaying to their users.
- è This problem appears to be comming from a badly
- formatted Node record in the Message file.
- STATUS: Either run CONFIG and creat a new
- MESSAGES file on a newly formatted disk or
- run the quick and dirty BASIC program SNOOP.BAS
- against your current MESSAGES file -- after you
- have backed it up of course!! SNOOP.BAS is
- available for downloading.
-
- RBBS-PC BAS 12/29/85 Q>uick Scan of messages whose message numbers
- EXE were less than four digits didn't display the
- subject of the message.
- STATUS: Line 4590 should read as follows:
-
- 4590 IF QUICK.SCAN.MESSAGENS THEN _
- A$=FNSS$(LEFT$(MESSAGE.RECORD$,5))+" "+SJ$ : _
- GOSUB 1405 : _
- GOTO 4630
-
- RBBS-PC BAS 12/29/85 Variable MAXIMUM.NUMBER.OF.NODES misspelled.
- EXE STATUS: Change the variable in line 118 from
- MAXIUM.NUMBER.OF.NODES
- to
- MAXIMUM.NUMBER.OF.NODES
-
- =================End of Reported Bugs/Fixes for CPC13-1A=================